Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1440

reference: 117-tree-1
name: 1440
tree-preservation-order: undefined
117-tpo-1
uprn
address-text
point: POINT (-1.030671 50.866482)
geometry: MULTIPOLYGON (((-1.030600 50.866474,-1.030603 50.866488,-1.030613 50.866501,-1.030629 50.866511,-1.030649 50.866517,-1.030670 50.866520,-1.030692 50.866518,-1.030712 50.866511,-1.030728 50.866502,-1.030739 50.866489,-1.030742 50.866475,-1.030739 50.866461,-1.030729 50.866449,-1.030714 50.866439,-1.030694 50.866432,-1.030672 50.866430,-1.030650 50.866432,-1.030630 50.866438,-1.030614 50.866448,-1.030604 50.866460,-1.030600 50.866474)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL